<html>
<head><meta charset="utf-8"><title>maintaining the reference · t-lang · Zulip Chat Archive</title></head>
<h2>Stream: <a href="https://rust-lang.github.io/zulip_archive/stream/213817-t-lang/index.html">t-lang</a></h2>
<h3>Topic: <a href="https://rust-lang.github.io/zulip_archive/stream/213817-t-lang/topic/maintaining.20the.20reference.html">maintaining the reference</a></h3>

<hr>

<base href="https://rust-lang.zulipchat.com">

<head><link href="https://rust-lang.github.io/zulip_archive/style.css" rel="stylesheet"></head>

<a name="194983636"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/213817-t-lang/topic/maintaining%20the%20reference/near/194983636" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nikomatsakis <a href="https://rust-lang.github.io/zulip_archive/stream/213817-t-lang/topic/maintaining.20the.20reference.html#194983636">(Apr 22 2020 at 19:58)</a>:</h4>
<p>So <span class="user-mention" data-user-id="120518">@Eric Huss</span> was raising with me the question of how best to maintain the reference. I definitely think that we should be taking a more active maintaince role here -- I'm curious <span class="user-group-mention" data-user-group-id="1977">@T-lang</span> to hear any thoughts about this. In my ideal world, we'd be doing more work to actively complete the reference as well as maintain it.</p>



<a name="194983676"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/213817-t-lang/topic/maintaining%20the%20reference/near/194983676" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nikomatsakis <a href="https://rust-lang.github.io/zulip_archive/stream/213817-t-lang/topic/maintaining.20the.20reference.html#194983676">(Apr 22 2020 at 19:58)</a>:</h4>
<p>One thing I could see doing, for example, is making it part of the duty of membership in t-lang to review PRs</p>



<a name="194983683"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/213817-t-lang/topic/maintaining%20the%20reference/near/194983683" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nikomatsakis <a href="https://rust-lang.github.io/zulip_archive/stream/213817-t-lang/topic/maintaining.20the.20reference.html#194983683">(Apr 22 2020 at 19:58)</a>:</h4>
<p>e.g., we could setup high-five</p>



<a name="194984078"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/213817-t-lang/topic/maintaining%20the%20reference/near/194984078" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/213817-t-lang/topic/maintaining.20the.20reference.html#194984078">(Apr 22 2020 at 20:01)</a>:</h4>
<p>I certainly don't ind reviewing reference PRs.</p>



<a name="194984132"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/213817-t-lang/topic/maintaining%20the%20reference/near/194984132" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/213817-t-lang/topic/maintaining.20the.20reference.html#194984132">(Apr 22 2020 at 20:01)</a>:</h4>
<p>Seems like there are two separate issues as well: who will handle the current gaps between the reference and the Rust language, and who will take responsibility for adding <em>new</em> things to the reference when we change the language.</p>



<a name="194984179"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/213817-t-lang/topic/maintaining%20the%20reference/near/194984179" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nikomatsakis <a href="https://rust-lang.github.io/zulip_archive/stream/213817-t-lang/topic/maintaining.20the.20reference.html#194984179">(Apr 22 2020 at 20:02)</a>:</h4>
<p>Yes.</p>



<a name="194997809"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/213817-t-lang/topic/maintaining%20the%20reference/near/194997809" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Eric Huss <a href="https://rust-lang.github.io/zulip_archive/stream/213817-t-lang/topic/maintaining.20the.20reference.html#194997809">(Apr 22 2020 at 22:14)</a>:</h4>
<p>Yea, there are various degrees of things that would be helpful:</p>
<ul>
<li>People to review PRs.</li>
<li>People responding to and triaging issues.</li>
<li>People working on bugs, inaccuracies.</li>
<li>People working on big projects (new content).</li>
</ul>
<p>I'd also like to talk about the permissions on the repo itself. Right now I can't merge my own changes, so I'm reluctant to even work on formatting fixes if nobody can approve them. Some options here:</p>
<ul>
<li>Add more people to the team, and give them write permissions.</li>
<li>Remove branch protections so I can just merge my own small changes (not sure how people feel about that).</li>
<li>Switch to homu (or bors-ng?), and just give all of t-lang approval (this might be my preferred approach, though my success in getting things like this done is poor).</li>
</ul>



<a name="195001399"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/213817-t-lang/topic/maintaining%20the%20reference/near/195001399" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nikomatsakis <a href="https://rust-lang.github.io/zulip_archive/stream/213817-t-lang/topic/maintaining.20the.20reference.html#195001399">(Apr 22 2020 at 22:58)</a>:</h4>
<p><span class="user-mention" data-user-id="120518">@Eric Huss</span> so I think we ought to create a wg-reference or something to manage the permissions, and give that group write access, and create a highfive. We can make a stream, too. The biggest thing to think about is who will "lead" the group, and how much active work we want to put into that.</p>



<a name="195002153"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/213817-t-lang/topic/maintaining%20the%20reference/near/195002153" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Eric Huss <a href="https://rust-lang.github.io/zulip_archive/stream/213817-t-lang/topic/maintaining.20the.20reference.html#195002153">(Apr 22 2020 at 23:07)</a>:</h4>
<p>There's already a <code>reference</code> team at <a href="https://github.com/rust-lang/team/blob/master/teams/reference.toml" title="https://github.com/rust-lang/team/blob/master/teams/reference.toml">https://github.com/rust-lang/team/blob/master/teams/reference.toml</a>, and is a "subteam" of lang.  I'm uncertain how this is currently connected to github permissions (I'm under the impression it is not connected).  I'm also unsure what "subteam" actually means (like does it automatically give lang members r+ rights if we had bors set up?).</p>



<a name="195433580"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/213817-t-lang/topic/maintaining%20the%20reference/near/195433580" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nikomatsakis <a href="https://rust-lang.github.io/zulip_archive/stream/213817-t-lang/topic/maintaining.20the.20reference.html#195433580">(Apr 27 2020 at 15:25)</a>:</h4>
<p><span class="user-mention" data-user-id="120518">@Eric Huss</span> yes, that does not appear to be sync'd with github, we should fix that. The general procedure these days is to try and avoid giving access rights to individuals, only to teams. I suspect we want to give write access to both lang + this group</p>



<a name="195608757"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/213817-t-lang/topic/maintaining%20the%20reference/near/195608757" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nikomatsakis <a href="https://rust-lang.github.io/zulip_archive/stream/213817-t-lang/topic/maintaining.20the.20reference.html#195608757">(Apr 28 2020 at 18:43)</a>:</h4>
<p>I'm cc'ing <span class="user-mention" data-user-id="228912">@James Munns</span> and <span class="user-mention" data-user-id="215333">@Florian Gilcher</span> into this conversation, as it's relevant to Sealed Rust</p>



<a name="195803446"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/213817-t-lang/topic/maintaining%20the%20reference/near/195803446" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> RalfJ <a href="https://rust-lang.github.io/zulip_archive/stream/213817-t-lang/topic/maintaining.20the.20reference.html#195803446">(Apr 30 2020 at 06:51)</a>:</h4>
<p>when it comes to MIR semantics and unsafe code concerns, I could also help with reference maintenance</p>



<hr><p>Last updated: Aug 07 2021 at 22:04 UTC</p>
</html>